Repository navigation
Adjust callout guidance - #270
Conversation
Thank you!Thank you for your pull request 😃 🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}. If you have files that automatically render output (e.g. R Markdown), then you should check for the following:
Rendered Changes🔍 Inspect the changes: https://github.com/carpentries/sandpaper-docs/compare/md-outputs..md-outputs-PR-270 The following changes were observed in the rendered markdown documents: What does this mean?If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible. This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation. ⏱️ Updated at 2026-02-06 13:33:22 +0000 |
Now that we have a
spoilerclass of fenced div, I prefer to encourage developers of new lessons to use that for optional content, asides, etc. I think thecalloutcallout is best used for the opposite: to draw attention to a particularly important point. That is the advice we give in Collaborative Lesson Development Training and this PR updates the Component Guide to match.